Airbnb Market Monitor — Public Listing Search + Detail Monitoring

Monitor Airbnb markets with one actor instead of stitching together separate search dumps and one-off room scrapes. This actor pulls public search results, enriches each listing from the room detail page, and returns the fields STR analysts actually use: nightly pricing, total stay pricing, ratings, host quality, amenities, rules, and neighborhood context.

No login and no private API bypasses required for the validated core flow.

Why this exists

The validated wedge is not “another Airbnb scraper.” Buyers already have that. What they are missing is a reliable monitor-first actor that combines:

• public search-result coverage
• room-detail enrichment
• recurring snapshots for price/review/host deltas
• built-in market summary metrics per location

The niche leader has adoption, but weak satisfaction and support. This actor is shaped around recurring market intelligence, not raw row dumping.

Best-fit buyers

• STR market-intelligence teams
• hosts and property managers tracking comps
• real-estate and vacation-rental analysts
• agencies benchmarking nightly pricing and listing quality
• data vendors building recurring listing-monitor feeds

What you get

Per listing:

• listing ID and canonical room URL
• title, room type, area/location label
• lat/lng
• guests, bedrooms, beds, baths
• nightly price and total price for selected dates when present
• rating and review count
• host name, host ID, superhost flag
• guest-favorite badges
• amenities summary
• photo URLs
• house-rules summary
• neighborhood / getting-around text when surfaced
• capture timestamp

Per location report:

• nightly-price min / p25 / median / mean / p75 / max
• total-price stats
• average rating
• median review count
• superhost rate
• guest-favorite rate
• room-type breakdown
• top amenities across the market snapshot

Example input

{
  "searchTerms": ["paris", "austin texas"],
  "maxItemsPerSearch": 30,
  "includeItemDetails": true,
  "checkIn": "2026-06-22",
  "checkOut": "2026-06-27",
  "adults": 1,
  "proxyConfiguration": { "useApifyProxy": true }
}

Example output row

{
  "recordType": "listing",
  "query": "paris",
  "listingId": "36276450",
  "canonicalUrl": "https://www.airbnb.com/rooms/36276450",
  "title": "A quiet little corner in the heart of Paris",
  "roomType": "Room in Paris",
  "cityArea": "Montreuil",
  "nightlyPrice": 81.53,
  "totalPriceForDates": 462.88,
  "currency": "€",
  "ratingValue": 4.94,
  "reviewCount": 633,
  "hostName": "Claire",
  "superhost": true,
  "amenitiesSummary": ["Kitchen", "Wifi", "Dedicated workspace"],
  "capturedAt": "2026-06-04T12:00:00.000Z"
}

Example market report

{
  "recordType": "marketReport",
  "query": { "location": "paris", "market": "global", "checkIn": "2026-06-22", "checkOut": "2026-06-27" },
  "listingCount": 30,
  "nightlyPriceStats": { "currency": "€", "median": 118, "p25": 82, "p75": 176 },
  "averageRating": 4.81,
  "reviewCountMedian": 91,
  "superhostRate": 46.67,
  "guestFavoriteRate": 33.33
}

Recurring use cases

• daily or weekly city snapshot monitoring
• price change tracking on comp sets
• guest-favorite / superhost mix tracking
• review-count and rating drift monitoring
• new-listing and delisting monitoring
• host portfolio quality benchmarking

Reliability and risk posture

Validated flow: public homepage, search pages, and room detail pages returned plain HTTP 200 in live probing. The actor stays HTTP-first with got-scraping, homepage cookie minting, re-mint on block, and Apify Proxy support.

Robots posture for Airbnb is restrictive. This actor is therefore positioned only around public page extraction for monitoring use cases. It does not market private review-path/API bypasses.

Practical note

The hardened template was eBay-shaped, so the minimal pragmatic change here was to replace the eBay-specific engine wiring in src/main.ts and src/cli.ts to point at a new src/target.ts Airbnb implementation while preserving the same session/retry/proxy pattern and the rest of the packaging/build flow.